pull: Always scan for commit object, even if ref is unchanged
authorColin Walters <walters@verbum.org>
Tue, 23 Jul 2013 23:36:15 +0000 (19:36 -0400)
committerColin Walters <walters@verbum.org>
Tue, 23 Jul 2013 23:36:15 +0000 (19:36 -0400)
commit688d8f176b6c6d566226ca29304ecfd53c199889
treee63b3fa9f79a8dd4ab67767178f347cc72e2fabd
parent3ea62abe7546b9e929ddb02d74277b755be6a3c8
pull: Always scan for commit object, even if ref is unchanged

If the admin encounters corruption and does:

$ ostree admin fsck --delete

We want them to be able to recover the objects easily from the
network; with this patch, they do:

$ ln -s dummyvalue /ostree/repo/transaction
$ ostree refs --delete remotename:branchname
$ ostree pull remotename

This patch avoids the need for the refs --delete; we might as well
force scan the commit, and with this patch we still print that it
changed.
src/libostree/ostree-repo-pull.c